Skip to content

Run CI / CodeQL / Dependency Review on develop pull requests#191

Closed
kirich1409 wants to merge 1 commit into
developfrom
chore/ci-trigger-develop
Closed

Run CI / CodeQL / Dependency Review on develop pull requests#191
kirich1409 wants to merge 1 commit into
developfrom
chore/ci-trigger-develop

Conversation

@kirich1409
Copy link
Copy Markdown
Contributor

Why

The repo uses main (released code) + develop (integration). The develop ruleset requires status checks Build Android, Build Docs, and Build iOS, but the workflows producing those checks are configured with pull_request.branches: [ main ] only. PRs targeting develop (e.g. #190) therefore never run the required checks and stay in mergeStateStatus: BLOCKED forever.

What

Add develop to PR triggers (and post-merge push triggers where appropriate) in four workflow files:

File push.branches pull_request.branches
.github/workflows/ci.yml [ main, develop ] [ main, develop ]
.github/workflows/codeql.yml [ main, develop ] [ main, develop ]
.github/workflows/dependency-review.yml [ main, develop ]
.github/workflows/docs.yml unchanged (main-only) adds - develop

docs.yml keeps push.branches: [ main ] because the publish-docs job gates on github.event_name == 'push' and pushes to GitHub Pages — Pages must stay main-only. publish.yml (Maven Central) is left untouched, also intentionally main-only.

No job step, action version, runner, permission, or concurrency group changed.

Verification

Once this PR lands in develop, re-trigger checks on #190 by either closing+reopening it or pushing an empty commit; the Build Android / Build Docs / Build iOS jobs will then register and unblock the merge.

Test plan

  • Build Android runs on this PR (proves the trigger fix works for develop PRs).
  • Build Docs runs.
  • Build iOS runs (macOS runner).
  • CodeQL Analyze Kotlin runs.
  • dependency-review runs.

🤖 Generated with Claude Code

The repo uses a main (released) + develop (integration) branching model.
The develop ruleset requires status checks Build Android, Build Docs, and
Build iOS, but the workflows producing those checks were configured to
trigger only on pull_request.branches: [main], so PRs targeting develop
never ran them and were permanently merge-blocked.

Add develop to the pull_request.branches list of ci.yml, docs.yml,
codeql.yml, and dependency-review.yml. Add develop to push.branches for
ci.yml and codeql.yml as well (post-merge integration validation).
Leave docs.yml push.branches at main-only — the publish-docs job gates
on github.event_name == 'push' and publishes to GitHub Pages, which
must remain main-only. publish.yml stays main-only.

No job, step, action, runner, permission, or concurrency change.
@kirich1409 kirich1409 closed this May 17, 2026
@kirich1409 kirich1409 deleted the chore/ci-trigger-develop branch May 17, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant